TMOD - Navigation and Tracking Services
Year 2000 Compliance Plan
(draft)
Prepared by:
Clifforrd R. Kettemborough, Y2K Task Manager
Approved by:
Edward J. Christensen, System Services Manager
January, 98
Jet Propulsion Laboratory
Concurrence Signature Page
Pieter Kallemeyn, System Services Development Engineer
Change Incorporation Log
Status
|
Pages Affected
|
Issue Date
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
- Introduction
- Purpose
- Document Scope
- Background
- Summary of Approach
- Reference Materials
- Controlling Documents
- Applicable Documents
- TMOD Navigation and Tracking System services Year 2000 Compliance
Requirements
- Sub-systems (components)
- Compliance Verification Methods
- General Integrity
- System Date
- Two-Digit Year Fields
- High-Risk Dates
- Time-outs, Delays, and Sleep Functions
- No Special Interpretation for Date Field Allowed
- Reinitialize Normally
- Correct Rollover of System dates
- Handle Non-compliant Input
- Dates on General Labels
- Dates on Hardcopy Reports
- Date Integrity
- Data Manipulation and Leap Year
- Dates from both Centuries
- Dates in Data Storage
- Date Conversion
- Overflow
- Dates within Playback data
- Pass-through Data
- Explicit Century
- Implicit Century
- Performance Requirements
- Reliability, Maintainability, and Related Requirements
- 3rd Party Software
- Implementation Plan
- Approach
- Constraints
- Organization, Roles, and Responsibilities
- Compliance
- Documentation Requirements
- Work Breakdown Structure
- Standards and Activities
- Process Support
- Engineering Methods, Tools, and Training
- Deliverables
- Acceptance Criteria and Qualification Methods
- Testing Approach
- Test Plan
- Test Procedures
- Test Cases
- Test Scripts
- Unit
- Integration
- System
- Regression
- Acceptance
- Verification and Validation
- Verification Methods
- Validation Methods
- Certification
- Schedule
- Priorities
- Resources
- Cost
Appendices
A. On Line Reference